hello, i am facing very strange issue while importing attributes from MV to FIM, while i import attributes from AD to MV, it sync full imformation but while sync from MV to FIM, it skips some attributes with status marked as "Skipped: Not Precedent" . i checked Presecence in Metaverse design and set to "set equal Precedence" but still i do not understand where i missed. please help Cheers, Mohit Goyal

Are you trying to export a NULL by any chance? A NULL will not overwrite an existing value. -Jeremy

no i am not exporting NULL, there are all values. if i check MV i can see values against each attribute but it does no show up in FIM.Cheers, Mohit Goyal

Did you run a full sync after changing the precedence? You should check your precedence configuration by using the FIM Object Visualizer. The script generates a report that is usually easier to read than what you see in the UI. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Hello Markus, I ran the FIM Object Visualizer and here are the details mentioned below , all seems okay but still i dont know where i missed Synchronization Rule Configuration Name inboud rule Description Created Time 4/22/2010 Precedence 2 Data Flow Direction Inbound Dependency Scope Metaverse Resource Type person External System AD MA External System Resource Type user Relationship Create Resource In FIM True Relationship Criteria ILM Attribute Data Source Attribute accountName sAMAccountName Inbound Attribute Flows Destination Source displayName displayName firstName givenName objectSid objectSid accountName sAMAccountName lastName sn department department officeFax facsimileTelephoneNumber city l officeLocation physicalDeliveryOfficeName jobTitle title postalCode postalCode address streetAddress company company domain CustomExpression(IIF(Eq(Left(ConvertSidToString(objectSid),41),"S-1-5-21-2873785770-2363925281-2547537135"),"ABC","RIGHT")) email mail manager manager telephoneNumber telephoneNumber country c The OutBound Sync rule is Synchronization Rule Configuration Name outbound rule Description outbound rule Created Time 4/22/2010 Precedence 1 Data Flow Direction Outbound Dependency Scope Metaverse Resource Type person External System AD MA External System Resource Type user Relationship Create Resource In External System True Enable Deprovisioning False Relationship Criteria ILM Attribute Data Source Attribute accountName sAMAccountName Initial Outbound Attribute Flows Allow Nulls Destination Source false unicodePwd Constant: Passw0rd1! false userPrincipalName +(accountName,"@abc.local") false employeeID employeeID false dn +("CN=",displayName,",OU=FIMObjects,DC=ABC,DC=local") false userAccountControl Constant: 512 Persistent Outbound Attribute Flows Allow Nulls Destination Source false sAMAccountName accountName false displayName displayName false givenName firstName false sn lastName false streetAddress address false assistant assistant false l city false company company false c country false department department false employeeType employeeType false title jobTitle false mailNickname mailNickname false manager manager false middleName middleName false facsimileTelephoneNumber officeFax false physicalDeliveryOfficeName officeLocation false telephoneNumber officePhone false postalCode postalCode Cheers, Mohit Goyal

can anybody helo me out....where is missed anything that it is not flowing all data to portalCheers, Mohit Goyal

If you have verified, that the attribute for which you get a "Skipped: Not Precedent" is configured to use equal precedence, and if you a full synchronization doesn't change anything, you need to contact product support. As a last resort, all you can do is to delete your connector spaces and re-initialize your environment again. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation